OS multi boot integrator

ABSTRACT

A computer implemented method of monitoring and integrating changes made to a computer system having a plurality of operating systems installed thereon is provided. The method monitors and records changes in accordance with user preferences for a first operating system. When the computer is booted for use with a second operating system, the method integrates into the second operating system and associated programs the changes made during operation of the computer with the first operating system.

BACKGROUND OF THE INVENTION

1. Field of the Invention

The present invention relates to the field of computers and, moreparticularly to an operating system (OS) multi boot integrator.

2. Description of the Related Art

The use of computers, especially the personal computer (PC) has becomewidespread. The computing power of the PC, whether coupled to a networkor operating as a stand-alone device, has increased significantly withthe development of new computer architectures. Newer operating systems(OS) have been developed to take advantage of the ever increasingcomputing power.

A computer operating system is a collection of software programs whichcontrol the execution of application programs running on the computer.Typically, an operating system manages the interaction of the computerhardware and software running on the computer by providing services tothe software applications such as resource allocation, scheduling oftasks, data management and input and output (I/O) control. The loadingof an operating system into the computer's memory is known as “booting”the OS. The reloading of an operating system (typically performed afterresetting the computer) is known as “rebooting” the OS.

A computer user is free to purchase and install an operating system thatdiffers from the one installed on the computer when it was purchased.Today, there are numerous commercially available operating systems tochoose from including, but not limited, to MS-DOS, UNIX, LINUX, OS/2,WINDOWS 3.x, WINDOWS NT, and WINDOWS 95.

Although these operating systems perform similar tasks, and many arecapable of running the same application programs, each operating systemhas its own strengths. Sometimes a user wishing to capitalize on thestrengths of these operating systems will install more than one OS onthe same computer. Commercially available software utilities aid a userin installing additional operating systems on their computers. Theseutilities also allow a user to choose which operating system to bootwhile a computer is being powered-on or reset. The capability to bootdifferent operating systems on the same computer is often referred to asan OS multi boot or multi booting.

Having more than one operating system on the same computer is notwithout its problems. One problem arises when a user installs anapplication program, such as, for example, a “browser” for the INTERNET,on a PC operating with a first operating system (OS #1). The user setsup communication and user settings for the browser, uses the browser andsaves a few bookmarks for interesting sites found while browsing theINTERNET. The user subsequently boots his computer with a secondoperating system (OS #2), but cannot use the browser since it wasinstalled for OS #1. The user would have to re-install the browser forOS #2 and then set up the communication and user settings for the newlyinstalled browser. The bookmarks for the browser installed for OS #2would have to be updated to include the bookmarks saved for OS #1.

If the user operates the browser installed for OS #2, and modifies anysettings or bookmarks, then the user would have to boot the computer inOS #1 and manually update the browser's settings and bookmarks to keepthe browsers settings consistent between OS #1 and OS #2. This takestime and can lead to mistakes particularly for applications which arefar more complicated than a browser. More complicated applications, forexample, may be too difficult for a user to integrate in an OS multiboot environment. Accordingly, there is a desire and need toautomatically integrate application programs and their settings betweenmultiple operating systems installed in an OS multi boot environment.

Similar problems arise when a user attempts to coordinate the userinterface, settings and preferences of the multiple installed operatingsystems. Any setting that were changed for OS #1 would have to bemanually changed for OS #2 (after a reboot). Likewise, settings thatwere changed for OS #2 would have to be manually changed for OS #1(after a reboot). This also takes time and may lead to mistakesparticularly for a user unfamiliar with computers. Accordingly, there isa desire and need to automatically integrate the settings andpreferences of multiple operating systems installed in an OS multi bootenvironment.

SUMMARY OF THE INVENTION

The present invention provides a method to automatically integrateapplication programs and their settings between multiple operatingsystems installed in an OS multi boot environment.

The present invention also provides a method to automatically integratethe settings and preferences of multiple operating systems installed inan OS multi boot environment.

The above and other features and advantages of the invention areachieved by a computer implemented method of monitoring and integratingchanges made to a computer system having a plurality of operatingsystems installed thereon. The method monitors and records changes inaccordance with user preferences for a first operating system. When thecomputer is booted for use with a second operating system, the methodintegrates into the second operating system and associated programs thechanges made during operation of the computer with the first operatingsystem.

BRIEF DESCRIPTION OF THE DRAWINGS

The foregoing and other advantages and features of the invention willbecome more apparent from the detailed description of the preferredembodiments of the invention given below with reference to theaccompanying drawings in which:

FIG. 1 illustrates the OS multi boot integrator method of one embodimentof the present invention;

FIG. 2 illustrates an exemplary computer system for implementing the oneembodiment of the method of the present invention;

FIG. 3 illustrates in flowchart form an exemplary OS multi bootintegration process performed by a method of the present invention;

FIG. 4 illustrate an exemplary monitor processing performed by a methodof the present invention; and

FIG. 5 illustrates an exemplary user configuration processing performedby a method of the present invention.

DETAILED DESCRIPTION OF PREFERRED EMBODIMENTS

FIG. 1 illustrates the OS multi boot integrator method 150 of oneembodiment of the present invention. As will be described below, themethod 150 is preferably operated on a computer system having an OSmulti boot capability, that is, the computer system has more than oneoperating system installed therein and is capable of booting any of theoperating systems upon a power-up or reset condition. In addition, themethod 150 may also be operated on a computer having one OS that isconnected via a network to a second computer with a different OS.

It is desirable for the method 150 to be initiated as soon as the bootedoperating system becomes operational and that the method 150 remainsrunning for as long as the system remains on. This may be achieved byany technique available to the OS that has been booted. For example, acomputer system booted with WINDOWS 95 could initiate the method 150from a “startup” group (a startup group contains application programs tobe executed every time the OS starts).

The method 150 includes OS multi boot integration processing 200,monitor processing 300 and user configuration processing 350 tasks(described in detail below with reference to FIGS. 3-5). FIG. 1 showsthe three tasks 200, 300, 350 being performed in a parallel manner(i.e., all running at the same time), but it must be noted that tasks200, 300, 250 can be performed sequentially or in any other mannerallowable by the booted OS. In addition, it must be noted that themethod 150 does not have to be split into the three identifiable tasks200, 300, 350 illustrated in FIG. 1 and that any number of tasks can beused to perform the present invention.

Referring now to FIG. 2, the OS multi boot integrator method 150 of thepresent invention runs on a programmed general purpose computer system100. The computer system 100 includes a central processing unit (CPU)102 that communicates with an input/output (I/O) device 104 over a bus130. Additional I/O devices 106, 120, 122 are illustrated, but are notnecessary. The computer system 100 also memory 108, read only memory(ROM) 110, and may include peripheral devices such as a floppy diskdrive 112 and a compact disk (CD) ROM drive 114 which also communicatewith the CPU 102 over the bus 130. It must be noted that the exactarchitecture of the computer system 100 is not important and that anycombination of computer compatible devices may be incorporated into thesystem 100 as long as the OS multi boot integrator method 150 of thepresent invention can operate on the system 100 as described below withreferences to FIGS. 3-5. Moreover, the program for CPU 102 which causesit to implement the method 150 of the present invention may be stored inmemory 108, ROM 110, CD-ROM 118, floppy disk 116, a hard drive or anyother medium capable of storing a program. During execution of theprogram it will be loaded into the main memory of the CPU (not shown).All of these devices communicate with CPU 102 as is well known in theart.

The CPU 102 performs any logical and mathematical operations required bythe method 150 of the present invention, such as data manipulation andcomparisons, as well as other arithmetic and logical functions generallyunderstood by those of ordinary skill in the art. The memory 108 is usedto store data and program instructions required to implement the method150 of the present invention and can be comprised of conventional randomaccess memory (RAM), dynamic random access memory (DRAM), bulk storagememory, or any combination thereof, as generally understood by those ofordinary skill in the art. In addition, the memory 108 will contain atleast two installed operating systems allowing the computer system 100to have a multi boot capability. The I/O devices 104, 106, 120, 122 areresponsible for interfacing with an operator of the computer system 100or with peripheral data devices such as a hard drive or other device(not shown) to receive or distribute data as generally understood bythose of ordinary skill in the art. Typical I/O devices include akeyboard, mouse, and display.

Any conventional technique can be used to install the multiple operatingsystems into the memory 108. Currently, there exists numerouscommercially available utilities for such purposes. These utilities,such as V Communications'SYSTEM COMMANDER, for example, will alsoprovide the capability to selectively boot one of the operating systemsout of the memory 108 and into the main memory of the CPU 102 (notshown). Typically, the utilities provide some form of menu orinstruction screen to allow a computer user to choose which OS to bootand if the user does not choose an OS to boot, the utility will boot a“default” OS. It must be noted that the technique used to install orboot the operating systems is not important and the invention should notbe limited to any specific technique.

Referring again to FIG. 1, a brief description of the method 150 of thepresent invention will be provided. A detailed description will followwith references to FIGS. 3-5. To aid in the discussion, “OS #1” will beused to refer to one installed operating system while “OS #2” will beused to refer to a different installed operating system. It must benoted that the method 150 of the present invention will operateregardless of the booted OS.

Briefly, and presuming that OS #1 has been booted, the monitorprocessing 300 will record changes made to operating system settingsfiles, user applications, data files and any newly installed oruninstalled application programs. Operating system setting files arefiles used by the OS to manage the hardware, software and userpreferences. An example of a typical operating system settings file is aregistry file used by WINDOWS NT and WINDOWS 95. When OS #2 is booted,the OS multi boot integration processing 200 will examine and integratethe changes recorded for OS #1. Meanwhile, the monitor processing 200will record additional changes made to system settings, data files, etc.for OS #2 (so these changes will eventually be integrated into OS #1).The user configuration processing 350 allows the user to determine thelevel of integration (i.e., the types of changes to be integratedbetween the multiple operating systems).

The changes made for the monitored OS will be recorded in a “recordchange” file which is accessible by the method 150 of the presentinvention regardless of the booted OS. As will be described below withreference to FIG. 4, the record change file will include only theinformation which the user has selected to be monitored. For example, ifthe user is only interested in whether new applications have beeninstalled, then the record change file will only include informationconcerning new installations. It may also be desirable for the recordchange file to include an operating system identifier (OS ID) todetermine which operating system has undergone the change. This willprevent changes made under OS #1 from being deleted if OS #1 is rebootedprior to OS # 2 being booted. If there are three or more installedoperating systems, for example, the OS ID will be useful to ensure thatall of the operating systems are integrated with the recorded changes.

FIG. 3 illustrates one example of the OS multi boot integrationprocessing 200 performed by the method 150 of the present invention.Presuming OS #1 is currently booted, the processing 200 will examine thechange record file (step 202) to determine what changes were recorded bythe present invention for OS #2 (and any other installed OS). Once thechange record file has been examined, the processing determines whethera new application program was installed (step 204). If no newapplication program was installed for OS #2, or if the user has chosennot to have newly installed application programs recorded, theprocessing continues at step 214. If it has been determined that a newapplication program was installed for OS #2, an application installationroutine is initiated (step 206). The application installation routinewill alert the user that a new application program was installed for OS#2 and prompt the user if this application program should be installedfor OS #1 (step 208). The application installation routine willcoordinate the following steps required to properly install and setupthe new application program.

At step 210, it is determined if the user wants to install the newapplication program. If the user decides not to install the newapplication program, the processing continues at step 214 to determineif any file changes for OS #2 need to be integrated. If the user wishesto install the new application program, the application program isinstalled in the same directory as it was installed for OS #2, if theapplication program allows it, or in a new directory if the applicationprogram does not allow a second installation in the same directory (step212). In addition, any user settings, data files, etc. required by thenewly installed application program (for OS #1) will be copied from thesettings, data files, etc. saved for OS #2. Thus, the applicationprogram will be installed to run on both OS #1 and OS #2 and will alsobe configured the same. Once the application program has been installedand setup, the processing continues at step 214 to determine if any filechanges for OS #2 need to be integrated. It must be noted, that althoughnot shown in FIG. 3, the processing 200 would check the record changefile for additional newly installed application programs and loopthrough steps 204 to 212 to install and integrate them.

At step 214 it is determined if any “data” file changes made for OS #2need to be integrated for OS #1. Data files can be application programfiles such as bookmarks for an INTERNET browser. If no data file changesneed to be integrated, or if the user has decided not to integrate datafile changes, the processing continues at step 220 to determine if anyOS settings file changes need to be integrated. If there were data filechanges, the processing determines and modifies any OS specificreferences so that they reference the current OS (216). That is, anydata file change pointing to OS #2 or otherwise setup for OS #2 wouldhave to be verified that they could be suitable for use with OS #1 andthen modified to reference OS #1. Once the data file changes aremodified for OS #1, they are copied into the appropriate OS #1 data file(step 218). In addition, where possible, the data file it self will becopied into the appropriate directory for OS #1. Once the data filechanges have been integrated, the processing continues at step 220 todetermine if any OS settings file changes need to be integrated. It mustbe noted, that although not shown in FIG. 3, the processing 200 wouldcheck the record change file for additional data file changes and loopthrough steps 214 to 218 to integrate them.

At step 220, it is determined if any OS settings file changes made forOS #2 need to be integrated for OS #1. If no OS settings file changesneed to be integrated, or if the user has decided not to integrate OSsettings file changes, the processing 200 completes. If there were OSsettings file changes, the processing determines and modifies any OSspecific references so that they reference the current OS (step 222).That is, any OS settings file changes pointing to OS #2 or otherwisesetup for OS #2 would have to be verified that they could be suitablefor use with OS #1 and then modified to reference OS #1. Once the OSsettings file changes are modified for OS #1, they are merged into theappropriate OS #1 settings file (step 224). It must be noted, thatalthough not shown in FIG. 3, the processing 200 would check the recordchange file for additional OS settings file changes and loop throughsteps 220 to 224 to integrate them. At this point, the OS multi bootintegration processing 200 is completed. It must be noted that theprocessing 200 could be configured to prompt the user every time achange is going to be integrated if so desired.

FIG. 4 illustrates one example of the monitor processing 300 performedby the method 150 of the present invention. Presuming OS #1 is currentlybooted, the processing 300 will continuously monitor and record changesso that they may be integrated into OS #2 (and any other installed OS).At step 302, the monitor processing 300 determines what should bemonitored by examining user monitor settings (described below withreference to FIG. 5). As stated earlier, the user decides the level ofintegration. The user's decision is stored away in a user monitorsettings file. Depending upon the user monitor settings, the processingcontinues to steps 304, 306, 308. The three steps 304, 306, 308 areillustrated as being initiated in a parallel manner (i.e., all runningat the same time), but it must be noted that they can be initiatedsequentially or in any other manner allowable by the booted OS. Inaddition, it must be noted that the processing 300 does not have toutilize the three steps 304, 306, 308 as illustrated in FIG. 4 and thatany number of steps can be used to properly monitor changes in OSsettings files, data files and newly installed application programs.

In step 304, the processing 300 watches for changes in the OS settingsfiles. Changes are determined by examining and storing the currentsettings for OS #1 upon initiation of the monitor processing 300. Inaddition, the user monitor settings are examined to determine if anyspecific OS setting files should or should not be monitored. If an OSsettings file that the user wishes to be monitored is changed, thesechanges are recorded and subsequently placed into the change record file(step 310).

In step 306, the processing 300 watches for changes in the data files.Changes are determined by examining and storing the current settings forOS #1 upon initiation of the monitor processing 300. In addition, theuser monitor settings are examined to determine if any specific datafiles should or should not be monitored. If a data file that the userwishes to be monitored is changed, these changes are recorded andsubsequently placed into the change record file (step 310).

In step 306, the processing 300 watches for newly installed applicationprograms. Newly installed application programs are determined byexamining and storing the current application programs installed for OS#1 upon initiation of the monitor processing 300. If a new applicationprogram is installed, the appropriate information is recorded andsubsequently stored into the change record file (step 310). It must benoted that the monitor processing 300 can prompt the user every time achange has been detected. This gives the user a chance to integratechanges that were not previously desired and a chance to not integratechanges that were requested to be monitored.

FIG. 5 illustrates one example of the user configuration processing 350performed by the method 150 of the present invention. Presuming OS #1 iscurrently booted, the processing 350 will allow the user to decide thelevel of integration between OS #1 and the other the installed operatingsystems. The processing 350 begins by allowing the user to enter aconfiguration mode (step 352). This can be accomplished by anytechnique. For example, the processing 350 may be setup to detect aspecific character sequence (via keyboard entry) as an indication thatthe user wishes to enter the configuration mode. In addition, if the OSmulti boot integrator method 150 of the present invention utilizesgraphical user interface (GUI), a window or menu option can be providedand used to input when the user wishes to enter the configuration mode.

Upon detection that the user wishes to enter the configuration mode(step 352), information regarding the level of integration andmonitoring the user desires is input and stored into the user monitorsettings file (step 354). As noted earlier, the user decides whatinformation should be integrated and thus, monitored. The user candecide to integrate all changes, some changes or no changes at all. Theuser can decide, for example, to integrate all changes to OS settingsfiles, while choosing not to integrate newly installed applications.

For example, the user can broadly decide whether to integrate newapplication program installations, changes in the OS settings files anddata files. Once this decision is made, the user can decide whetherthere are specific OS settings files or data files to monitor andintegrate (or not to integrate). In addition, the user configurationprocessing 350 can be configured to allow the user to control promptsand displayed information. In addition, the processing 350 can utilize a“default” integration level allowing the user to set an integrationlevel that has already been setup. As stated above with reference toFIG. 4, the information stored in the user monitor settings file is usedby the monitor processing 300 which monitors and records only theinformation requested by the user.

It must be noted that the OS multi boot integrator method 150 of thepresent invention can be utilized on a computer having one OS that isconnected via a network to a second computer with a different OS. Forexample, a user logs onto a networked computer running OS #1 and themethod 150 of the present invention. The user installs an applicationprogram and then logs off. The installation is recorded by the presentinvention (as described above with reference to FIG. 4). The usersubsequently logs onto a second computer on the same network executingthe present invention, but running OS #2. The method 150 detects thenewly installed application program and prompts the user if it should beinstalled (as described above with reference to FIG. 3).

It must be noted that the exact information saved and recorded by thepresent invention is dependent upon OS and type of applications beinginstalled which may vary. In addition, it must be noted that the presentinvention can be used to monitor and integrate additional changes to acomputer system, such the as deletion or unistallation of programapplication, and is not to be limited data files, OS settings files andnewly installed application programs. It must be noted that the presentinvention can be setup to confirm selections and responses made by theuser if so desired.

It must be noted that the present invention is implemented as a programwhich gets executed on a computer system. The invention can be writtenin different computer languages for different computer systems. Thepresent invention can be stored on a hard drive, floppy disc, CD-ROM orother permanent or semi-permanent storage medium. The program embodyingthe present invention can also be divided into program code segments,downloaded, for example, from a server computer or transmitted as a datasignal embodied in a carrier wave as is known in the art.

While the invention has been described in detail in connection with thepreferred embodiments known at the time, it should be readily understoodthat the invention is not limited to such disclosed embodiments. Rather,the invention can be modified to incorporate any number of variations,alterations, substitutions or equivalent arrangements not heretoforedescribed, but which are commensurate with the spirit and scope of theinvention. Accordingly, the invention is not to be seen as limited bythe foregoing description, but is only limited by the scope of theappended claims.

What is claimed as new and desired to be protected by Letters Patent ofthe United States is:
 1. A computer implemented method for integratingchanges made to a computer system operating under a first operatingsystem into said computer system when operating under a second operatingsystem, said method comprising: recording at least one change to saidcomputer system made when operating under said first operating system,wherein a single processor is used to operate the computer system underboth the first operating system and the second operating system, andwherein the at least one recorded change is stored on a computerreadable medium coupled with the single processor; checking, while saidcomputer system is operating under said second operating system, for theat least one recorded change; applying said at least one recorded changeto the computer system while it is operating under said second operatingsystem; and repeating the checking and applying operations as often asnecessary to record any additional changes to said computer system madewhen operating under said first operating system.
 2. The method of claim1 further comprising the act of prompting a user to select if one ormore changes is to be applied, and applying only those changes whichsaid user selects to apply.
 3. The method of claim 1 wherein said atleast one recorded change comprises at least one change made to datafiles of said first operating system.
 4. The method of claim 3 furthercomprising: verifying that said at least one recorded change is suitablefor use or modifiable to be suitable for use with said second operatingsystem, wherein if said at least one recorded change is only modifiableit is modified to be suitable for use with said second operating system;and copying said verified or modified at least one change intocorresponding data files of said second operating system.
 5. The methodof claim 3 further comprising: verifying that the changed data files aresuitable for use with said second operating system; and using saidverified changed data files as data files of said second operatingsystem.
 6. The method of claim 1 wherein said at least one recordedchange to said computer system made when operating under said firstoperating system is recorded on a computer readable medium.
 7. Themethod of claim 1 wherein said at least one change comprises at leastone change made to operating settings files of said first operatingsystem.
 8. The method of claim 7 further comprising: verifying that saidat least one recorded change is suitable for use or modifiable to besuitable for use with said second operating system wherein if said atleast one recorded change is only modifiable it is modified to besuitable for use with said second operating system; and copying saidverified or modified at least one change into corresponding operatingsystem setting files of said second operating system.
 9. The method ofclaim 1 wherein said at least one recorded change comprises newapplication programs.
 10. The method of claim 9 further comprising theact of installing any new application programs previously installedunder said first operating system for said second operating system. 11.The method of claim 10 further comprising the act of setting up theinstalled application programs for said second operating system based onparameters used to setup corresponding application programs of saidfirst operating system, wherein if the parameters are not suitable foruse with said second operating system, the parameters are modified to besuitable for use with said second operating system.
 12. The method ofclaim 1 wherein said first and second operating systems are installed ona single computer system having a capability to boot one of saidoperating systems.
 13. A computer implemented method of monitoring andintegrating the changes made to a computer system operating under afirst operating system into said computer system when operating under asecond operating system, said method comprising: inputting, while saidcomputer system is operating under said first operating system,information representing features of said computer system to bemonitored; determining if any of the features corresponding to saidinput information were changed while said computer system is operatingunder said first operating system; storing at least one change on acomputer readable medium, wherein a single processor is used to operatethe computer system under both the first operating system and the secondoperating system, and wherein the at least one recorded change is storedon a computer readable medium coupled with the single processor; bootingsaid computer system with said second operating system; inputting saidat least one stored change from said computer readable medium; andapplying at least one stored change to the computer system whileoperating under said second operating system.
 14. The method of claim 13wherein said at least one stored change comprises changes made to datafiles of said first operating system.
 15. The method of claim 14 furthercomprising: verifying that said at least one recorded change is suitablefor use or modifiable to be suitable for use with said second operatingsystem, wherein if said at least one recorded change is only modifiableit is modified to be suitable for use with said second operating system;and copying said verified or modified at least one change intocorresponding data files of said second operating system.
 16. The methodof claim 14 further comprising: verifying that the changed data filesare suitable for use with said second operating system; and using saidverified change data files as data files of said second operatingsystem.
 17. The method of claim 13 wherein said at least one storedchange comprises changes made to operating system settings files of saidfirst operating system.
 18. The method of claim 17 further comprising:verifying that said at least one recorded change is suitable for use ormodifiable to be suitable for use with said second operating system,wherein if said at least one recorded change is only modifiable it ismodified to be suitable for use with said second operating system; andcopying said verified or modified at least one change into correspondingoperating system files of said second operating system.
 19. The methodof claim 13 wherein said at least one stored change comprises newapplication programs.
 20. The method of claim 19 further comprising theact of installing any new application programs previously installedunder said first operating system for said second operating system. 21.The method of claim 20 further comprising the act of setting up theinstalled application programs for said second operating system based onparameters used to setup corresponding application programs of saidfirst operating system, wherein if the parameters are not suitable foruse with said second operating system, the parameters are modified to besuitable for use with said second operating system.
 22. The method ofclaim 13 wherein said first and second operating systems are installedon a single computer system having a capability to boot one of saidoperating systems.
 23. A computer implemented method for integratingchanges made to a computer system operating under a first operatingsystem into said computer system when operating under a second operatingsystem, said method comprising: recording at least one change to saidcomputer system made when operating under said first operating systemwherein said at least one change comprises at least one change made tooperating settings files of said first operating system, wherein asingle processor is used to operate the computer system under both thefirst operating system and the second operating system, and wherein theat least one recorded change is stored on a computer readable mediumcoupled with the single processor; checking, while said computer systemis operating under said second operating system, for the at least onerecorded change; and applying said at least one recorded change to thecomputer system while it is operating under said second operatingsystem.
 24. A computer implemented method for integrating changes madeto a computer system operating under a first operating system into saidcomputer system when operating under a second operating system, saidmethod comprising: recording at least one change to said computer systemmade when operating under said first operating system, said changecomprising new application programs, wherein a single processor is usedto operate the computer system under both the first operating system andthe second operating system, and wherein the at least one recordedchange is stored on a storage medium coupled with the single processor;checking, while said computer system is operating under said secondoperating system, for the at least one recorded change; and applyingsaid at least one recorded change to the computer system while it isoperating under said second operating system.
 25. A computer implementedmethod for integrating changes made to a computer system operating undera first operating system into said computer system when operating undera second operating system, said method comprising: recording at leastone change to said computer system made when operating under said firstoperating system, wherein said at least one recorded change comprises atleast one change made to data files of said first operating system;checking, while said computer system is operating under said secondoperating system, for the at least one recorded change; applying said atleast one recorded change to the computer system while it is operatingunder said second operating system; repeating the checking and applyingoperations as often as necessary to record any additional changes tosaid computer system made when operating under said first operatingsystem; verifying that said at least one recorded change is suitable foruse or modifiable to be suitable for use with said second operatingsystem, wherein if said at least one recorded change is only modifiableit is modified to be suitable for use with said second operating system;and copying said verified or modified at least one change intocorresponding data files of said second operating system.
 26. A computerimplemented method for integrating changes made to a computer systemoperating under a first operating system into said computer system whenoperating under a second operating system, said method comprising:recording at least one change to said computer system made whenoperating under said first operating system, wherein said at least onerecorded change comprises at least one change made to data files of saidfirst operating system; checking, while said computer system isoperating under said second operating system, for the at least onerecorded change; applying said at least one recorded change to thecomputer system while it is operating under said second operatingsystem; repeating the checking and applying operations as often asnecessary to record any additional changes to said computer system madewhen operating under said first operating system; verifying that thechanged data files are suitable for use with said second operatingsystem; and using said verified changed data files as data files of saidsecond operating system.
 27. A computer implemented method forintegrating changes made to a computer system operating under a firstoperating system into said computer system when operating under a secondoperating system, said method comprising: recording at least one changeto said computer system made when operating under said first operatingsystem, wherein said at least one change comprises at least one changemade to operating settings files of said first operating system;checking, while said computer system is operating under said secondoperating system, for the at least one recorded change; applying said atleast one recorded change to the computer system while it is operatingunder said second operating system; repeating the checking and applyingoperations as often as necessary to record any additional changes tosaid computer system made when operating under said first operatingsystem; verifying that said at least one recorded change is suitable foruse or modifiable to be suitable for use with said second operatingsystem, wherein if said at least one recorded change is only modifiableit is modified to be suitable for use with said second operating system;and copying said verified or modified at least one change intocorresponding operating system setting files of said second operatingsystem.
 28. A computer implemented method for integrating changes madeto a computer system operating under a first operating system into saidcomputer system when operating under a second operating system, saidmethod comprising: recording at least one change to said computer systemmade when operating under said first operating system, wherein said atleast one recorded change comprises new application programs; checking,while said computer system is operating under said second operatingsystem, for the at least one recorded change; applying said at least onerecorded change to the computer system while it is operating under saidsecond operating system; repeating the checking and applying operationsas often as necessary to record any additional changes to said computersystem made when operating under said first operating system; installingany new application programs previously installed under said firstoperating system for second said operating system; and setting up theinstalled application programs for said second operating system based onparameters used to setup corresponding application programs of saidfirst operating system, wherein if the parameters are not suitable foruse with said second operating system, the parameters are modified to besuitable for use with said second operating system.
 29. A computerimplemented method of monitoring and integrating the changes made to acomputer system operating under a first operating system into saidcomputer system when operating under a second operating system, saidmethod comprising: inputting, while said computer system is operatingunder said first operating system, information representing features ofsaid computer system to be monitored; determining if any of the featurescorresponding to said input information were changed while said computersystem is operating under said first operating system; storing at leastone change on a computer readable medium, wherein said at least onestored change comprises changes made to data files of said firstoperating system; booting said computer system with said secondoperating system; inputting said at least one stored change from saidcomputer readable medium; applying at least one stored change to thecomputer system while operating under said second operating system;verifying that said at least one recorded change is suitable for use ormodifiable to be suitable for use with said second operating system,wherein if said at least one recorded change is only modifiable it ismodified to be suitable for use with said second operating system; andcopying said verified or modified at least one change into correspondingdata files of said second operating system.
 30. A computer implementedmethod of monitoring and integrating the changes made to a computersystem operating under a first operating system into said computersystem when operating under a second operating system, said methodcomprising: inputting, while said computer system is operating undersaid first operating system, information representing features of saidcomputer system to be monitored; determining if any of the featurescorresponding to said input information were changed while said computersystem is operating under said first operating system; storing at leastone change on a computer readable medium, wherein said at least onestored change comprises changes made to data files of said firstoperating system; booting said computer system with said secondoperating system; inputting said at least one stored change from saidcomputer readable medium; applying at least one stored change to thecomputer system while operating under said second operating system;verifying that the changed data files are suitable for use with saidsecond operating system; and using said verified changed data files asdata files of said second operating system.
 31. A computer implementedmethod of monitoring and integrating the changes made to a computersystem operating under a first operating system into said computersystem when operating under a second operating system, said methodcomprising: inputting, while said computer system is operating undersaid first operating system, information representing features of saidcomputer system to be monitored; determining if any of the featurescorresponding to said input information were changed while said computersystem is operating under said first operating system; storing at leastone change on a computer readable medium, wherein said at least onestored change comprises changes made to operating system settings filesof said first operating system; booting said computer system with saidsecond operating system; inputting said at least one stored change fromsaid computer readable medium; applying at least one stored change tothe computer system while operating under said second operating system;verifying that said at least one recorded change is suitable for use ormodifiable to be suitable for use with said second operating system,wherein if said at least one recorded change is only modifiable it ismodified to be suitable for use with said second operating system; andcopying said verified or modified at least one change into correspondingoperating system setting files of said second operating system.
 32. Acomputer implemented method of monitoring and integrating the changesmade to a computer system operating under a first operating system intosaid computer system when operating under a second operating system,said method comprising: inputting, while said computer system isoperating under said first operating system, information representingfeatures of said computer system to be monitored; determining if any ofthe features corresponding to said input information were changed whilesaid computer system is operating under said first operating system;storing at least one change on a computer readable medium, wherein saidat least one stored change comprises new application programs; bootingsaid computer system with said second operating system; inputting saidat least one stored change from said computer readable medium; applyingat least one stored change to the computer system while operating undersaid second operating system; installing any new application programspreviously installed under said first operating system for said secondoperating system; and setting up the installed application programs forsaid second operating system based on parameters used to setupcorresponding application programs of said first operating system,wherein if the parameters are not suitable for use with said secondoperating system, the parameters are modified to be suitable for usewith said second operating system.
 33. A computer implemented method forintegrating changes made to a computer system operating under a firstoperating system into said computer system when operating under a secondoperating system, said method comprising: recording at least one changeto said computer system made when operating under said first operatingsystem, wherein the at least one recorded change includes an operatingsystem identifier to indicate which operating system has undergone thechange; checking, while said computer system is operating under saidsecond operating system, for the at least one recorded change; applyingsaid at least one recorded change to the computer system while it isoperating under said second operating system, wherein the at least onerecorded change is only applied if the operating system identifierindicates that the change was made under a different operating system;and repeating the checking and applying operations as often as necessaryto record any additional changes to said computer system made whenoperating under said first operating system.